Design pattern - Interview Questions and Answers for 'Capgemini' | Search Interview Question - javasearch.buggybread.com

Javasearch.buggybread.com

Search Interview Questions

More than 3000 questions in repository.

There are more than 900 unanswered questions.
Click here and help us by providing the answer.

Have a video suggestion.
Click Correct / Improve and please let us know.

Submit Question

Design pattern - Interview Questions and Answers for 'Capgemini' - 2 question(s) found - Order By Newest

Very frequently asked.Usually among first few questions.

Q1. What is MVC ?

Ans. MVC is a Design Pattern that facilititates loose coupling by segregating responsibilities in a Web application

1. Controller receives the requests and handles overall control of the request
2. Model holds majority of the Business logic, and
3. View comprise of the view objects and GUI component

Help us improve. Please let us know the company, where you were asked this question :

_{Like Discuss Correct / Improve j2ee mvc mvc design pattern design pattern struts spring web application web frameworks ebay Asked in 60 Companies basic frequent}

Try 1 Question(s) Test

Related Questions

Explain Flow of Spring MVC ?

What are the benefits of using Spring Framework ?

Why Struts 1 Classes are not Thread Safe whereas Struts 2 classes are thread safe ?

What bean scopes does Spring support? Explain them.

Which MVC is struts2 based on ?

What are different modules of spring ?

What is Spring configuration file?

Q: What is default scope of bean in Spring framework?

What is bean auto wiring?

Q2. How one dao Implementation object (singleton) can handle multiple requests?

^{This question was recently asked at 'Capgemini'.This question is still unanswered. Can you please provide an answer.}

Help us improve. Please let us know the company, where you were asked this question :

_{Like Discuss Correct / Improve singleton Asked in 1 Companies}

Related Questions

Difference between Static and Singleton Class ?

What is the difference between Singleton and Prototype Bean scope in Spring ?

serialization and deserialization of singleton class

What is the difference between these two approaches of creating singleton Class ?

//Double Checked Locking Code
public static Singleton createInstance() {
   if(singleton == null){
      synchronized(Singleton.class) {
         if(singleton == null) {
            singleton = new Singleton();
         }
      }
   }
   return singleton;
}

//Single checked locking code
public static Singleton createInstance() {
   synchronized(Singleton.class) {
      if(singleton == null) {
         singleton = new Singleton();
      }
   }
   return singleton;
}

What are design situations to use Singleton and Prototype Design Pattern ?

How to avoid cloning, serialization in the singleton class ?

When singleton can break and how to resolve it

If you are given choice to either load object eagerly or lazily , which one would you use in case of singleton pattern ?

When should we use prototype scope and singleton scope for beans ?

Explain Singleton Design Pattern ?